failure 138:
Requirement failed: {setgid.06.02} error not met because its predicate (( priority_coverage == Priority_ReallyLow || ( priority_coverage == Priority_Unknown && setgid_spec == -1 ) ) && ( gid_coverage != Id_RealId && gid_coverage != Id_SavedSetId )) is false while error code EPERM is set ;
location |
trace |
/var/opt/lsb/test/olver-core/2013-07-25_08-37-08/process_meta_user_scenario.utz (process_meta_user_scenario.utt), line 59306 |
occurence |
scenario |
process_meta_user_scenario |
specification function |
setgid_spec() |
parameter value |
CallContext context = [pid=22601,thr=b7512700] |
parameter value |
GidT gid = 0 |
parameter value |
ErrorCode * @errno = EOK |
parameter value |
ErrorCode * errno = EPERM |
return value |
(IntT) -1 |
coverage & branch |
C ( Id, priority ) == ( Id_SavedSetId, Priority_ReallyLow ) |
properties |
REQ failed |
setgid.06.02 |
kind |
POSTCONDITION_FAILED |
similar known bug(s)
The setgid() function sets the real group ID, effective group ID, and the saved set-group-ID
of the calling process to the value, specified as its argument.
According to LSB, if this argument equals to the real group ID or the saved set-group-ID,
setgid() shall set the effective group ID to this value.
But on the target machine setgid() fails when trying to set the effective group ID to the
saved set-group-ID value.
Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102.
|
|